| Author |
Thread Statistics | Show CCP posts - 2 post(s) |

Eventy One
|
Posted - 2007.09.12 18:00:00 -
[1]
Ok. A billion people have pointed out the useless, but true, observation that "The Server is Down again".
I have two things to say about this:
1. Enough all ready. 2. Post some other true, but more useful observation such as - If CCP has used MySQL (and linux) instead of M$SQL (and Windows) - this likely would not be happening every time a patch is applied 
Enough Said. Eventy One
(CCP - Take a look at MySQL for heavens sake!)
|

Eventy One
|
Posted - 2007.09.12 18:07:00 -
[2]
Edited by: Eventy One on 12/09/2007 18:07:27
Originally by: Vandalias Problem: People spamming forums Solution: Start a new thread complaining about it
Brilliant!
To those who don't read a full post before posting, here is some hand holding ....
Look at point number two which makes a comment about which database CCP has chosen to use. Now look at the PS after the signature. It might be too great a gap for some intellects to jump, but the purpose of the post is actually there.
Still need some help? Thought so. Ill spell it out ... CCP is using M$SQL, and not MySQL. I'd bet 100 ISK that had CCP used MySQL few of these problems would occur.
No need to apologize. No need to thank me. (Move along, Move along - there are other posts you can troll)

Cheers Eventy
|

Eventy One
|
Posted - 2007.09.12 18:22:00 -
[3]
Originally by: Sandra Jones
Originally by: Eventy One
CCP is using M$SQL, and not MySQL. I'd bet 100 ISK that had CCP used MySQL few of these problems would occur.
MySQL is the best Choice for small and medium sized databases, but tbh, if it comes to the amount of data which is necessary for something like Eve, you realy want a solution which is designed for larger amounts of data then mysql is - and for larger amounts of concurent accesses too.
It might be a good idea to have someone compare the current solution with an oracle based one.
I've heard the argument that MySQL doesn't scale well before, but it just isn't my experience.
I have a pretty decent deployment that gets banged on pretty hard (billions of transactions a month - bursting up to thousands a second). Although I admit we did some glibc optimization to support good through-put before we rolled out redundant fail-over MySQL database expecting their to be problems. However, it isn't the DB that is the limiting factor - it is disk I/O.
Basically to get better performance than we're already getting, we need to upgrade the disks to 15k rpm drives or some other optimized storage solution.
It be interesting to see if the db errors are on the code end of Eve or on the native database performance end.
Cheers Eventy One
|

Eventy One
|
Posted - 2007.09.12 18:33:00 -
[4]
Originally by: CCP Wrangler Reopened.
Thanks. Appreciated.
Cheers Eventy One
|

Eventy One
|
Posted - 2007.09.12 18:37:00 -
[5]
Originally by: Epong Too much for Wrangler...OMG he's gonna down soon 

Not really his fault. This thread was meant to be about MySQL vs M$SQL - but he saw that thread title, and assumed it was yet another "server down" thread (kind of proving my point).
Cheers Eventy One
|

Eventy One
|
Posted - 2007.09.12 18:54:00 -
[6]
Originally by: XiticiX Much MUCH faster. The crashes are different though - this is most likely due to either corrupt data, locks on the database, or just plain bad coding practices which don't fail gracefully.
So corrupt data, locks on the db and so on are certainly withing the domain of the DB itself (i.e. M$SQL). I up my wager to 200 ISK that MySQL should have been the DB of choice!
Bad coding practices are within the domain of CCP however - but come on! They gave us EVE. Their coding can't be the problem, can it ... ?
Cheers Eventy One
|

Eventy One
|
Posted - 2007.09.12 19:34:00 -
[7]
Originally by: Winterblink None of this is to say that MySQL isn't capable of holding its own of course. It wouldn't be my first choice in terms of recommendation to a client, and the reason for that is one word: support. Argue that point until you're blue in the face, but most organizations feel more comfortable with the big names like Microsoft and Oracle.
You say correctly "argue that until you're blue in the face". The argument will come down to the those that say MySQL has no support, and those that point to MySQL.com as evidence to the contrary.
I'm definitely in the latter camp knowing that MySQL makes it money not on the DB but on their service, but I also realize perception is everything.
Cheers Eventy One
|

Eventy One
|
Posted - 2007.09.12 20:04:00 -
[8]
Originally by: Jimer Lins I find it extremely difficult to take anyone who uses terms like "M$SQL" seriously.
If you want to have an adult conversation, try to avoid using such childish terms; any point you may have had is immediately lost because people see that and you're instantly pigeonholed as not someone with an idea, but with an axe to grind, and they stop paying attention to anything you say.
Man u 31337!
Cheers Eventy One
(PS anyone think I scared the troll away? Good thing he didn't read past the M$SQL - he might have hung around!)
|

Eventy One
|
Posted - 2007.09.13 04:25:00 -
[9]
Originally by: James Lyrus I've no idea if this is still the case, but it _used_ to be the major reason why people used UNIX systems over WINtel - you could just get more IO through a highend SUN server, which had knock on implications for high end databases. The fact that Oracle can use raw devices for io too (I don't _think_ MS SQL can, but I don't know) just put the icing on it.
'scuse me. I do storage for a living, and I just get .... enthusisastic over ninja spec systems.
I'm not so sure any more with Sun running Intel architecture underneath. Many who purchase Sun don't even run Solaris any more (not saying that's a bad thing one way or the other) because they can run Linux with Intel. A Sun box just isn't a Sun any more.
As for M$SQL (used the dollar sign because I know Jimer Lins _loves_ it) scaling, I have my doubts, but I know Oracle has a good reputation in the enterprise world for a reason (especially on a *nix).
Cheers Eventy One
|

Eventy One
|
Posted - 2007.09.14 07:15:00 -
[10]
Originally by: Faridah
CCP is saying it's a DB problem. Which probably seems true since it's the DB who fall over and die, causing all the nodes to fall apart as they can't read/write to the DB.
However, it seems this problem started at a certain date and after that date the servers haven't been up 23 hrs. Unless they did some major changes in the DB I would think it could also be a external issue. Everyone with a little knowledge of relation DBs know that a misscoded INNER JOIN could wreck havoc on *any* DB, including mySQL, posgres .....
Woah! Stop right there! You said the P-word! Cheers Eventy One
|
| |
|